Skip to content

Conversation

@ShibalovRoman
Copy link
Contributor

Allow running SmartMove.exe from the CLI

-s | --source   = Mandatory 
-v | --vendor   = Mandatory

SmartMove command usage:

SmartMove.exe [-s config_file_name] [-v vendor] [-t target_folder] [-d domain] [-n] [-l LDAP_Account_unit] [-k]

Options:
-s | --source full path to the vendor configuration file
-v | --vendor vendor for conversion (available options: CiscoASA, JuniperSRX, JuniperSSG, FortiNet, PaloAlto, Panorama)
-t | --target migration output folder
-d | --domain domain name (for CiscoASA, JuniperSRX, JuniperSSG only)
-n | --nat ("-n false" |" -n true" [default]) convert NAT configuration [enabled by default]
-l | --ldap LDAP Account unit for convert user configuration option (for FortiNet, PaloAlto, and Panorama only)
-k | --skip ("-k false" |" -k true" [default]) do not import unused objects (for FortiNet, PaloAlto and Panorama only) [enabled by default]
-f | --format format of the output file (JSON[default], TEXT)

Example:
SmartMove.exe -s "D:\SmartMove\Content\config.txt" -v CiscoASA - t "D:\SmartMove\Content" -n true -k false -f json

@chkp-ofirs chkp-ofirs merged commit c4fa132 into CheckPointSW:master Jun 15, 2021
chkp-ofirs pushed a commit that referenced this pull request Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants